Systems and Methods for Managing PDP Contexts in a Wireless Data Communications Network

ABSTRACT

Systems and method are for managing packet data protocol (PDP) contexts in a wireless data communications network. A plurality of real-time applications are prioritized within a single, shared PDP context or allocated a second PDP context based upon priority levels logically assigned to the plurality of applications such that high priority applications are delivered before lower priority applications. Lower priority applications are suspended and interrupted by higher priority applications and are set to resume after the higher priority applications are completed. Priority levels are established by a priority management engine (PME) that may reside in one or more network elements, such as a General Packet Radio Service (GPRS) Support Node or a network probe system. The priority management engine establishes the priority levels based upon one or more factors including, for example, PDP utilization characteristics at a given time and/or given network location, and/or user preferences.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.12/707,791, filed Feb. 18, 2010, the entirety of which is hereinincorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to data communications networksand, more particularly, to systems and methods for managing packet dataprotocol (PDP) contexts in wireless data communications networks.

BACKGROUND

A PDP context provides a packet data connection over which a mobiledevice and a data network can exchange Internet protocol (IP) packets. APDP context has a record of parameters that consists of all the requiredinformation for establishing an end-to-end connection with the datanetwork. These parameters include a PDP type, a PDP address type, aQuality of Service (QoS) profile request (e.g., QoS parameters requestedby a user), a QoS profile negotiated by the data network, anauthentication type, and a Domain Name System (DNS) type (e.g., dynamicDNS or Static DNS).

The PDP Context is mainly designed to provide two specific functions forthe mobile device. The PDP Context is designed to allocate a PDPaddress, either an IP version 4 or an IP version 6 type address, to themobile device. The PDP context is also used to make a logical connectionwith a QoS profile, the set of QoS attributes negotiated for andutilized by one PDP context, through the data network.

Current, high-end mobile devices are capable of establishing multiplePDP contexts to serve parallel applications. These PDP contexts candiffer in their QoS parameters and/or the target data network to whichthey provide a data connection. By way of example, a mobile device canestablish a first PDP context to access the Internet through a webbrowser and a second PDP context to access an application provided by anapplication server.

Generally speaking, there are two types of PDP contexts, a primary PDPcontext, and a secondary PDP context. A primary PDP context has a uniqueassociated IP address. Primary PDP contexts can be activated ordeactivated independently from one another. A secondary PDP context iscreated based upon a primary PDP context and shares an IP address with aprimary PDP context. A secondary PDP context is always associated with aprimary PDP context. A PDP address (IP address) and access point (AP) isre-used from the primary PDP context. Thus, the primary and theassociated secondary PDP context provide connection to the same packetdata network with different guaranteed QoS.

One primary PDP context might have multiple secondary contexts assigned.Each PDP context has its own radio access bearer (RAB) and tunnel totransfer user plane data. The primary PDP context has to be active priorto activating an associated secondary PDP context. Any secondary PDPcontext can be deactivated while keeping the associated primary contextand any eventual other secondary PDP contexts active. If a primary PDPcontext is deactivated, this will also deactivate all the assignedsecondary PDP contexts. In 3GPP (3^(rd) Generation Partnership Project)networks, a total of 11 PDP contexts, including any combination ofprimary and secondary PDP contexts, may coexist simultaneously.

Each of multiple PDP Contexts can have different QoS profiles. A primaryPDP Context is a normal PDP Context with default QoS profile attributesand it is always activated first. For the multiple primary PDP Contexts,each context has a different PDP address and is used to attach to adifferent Packet Data Network (PDN) identified by a different AccessPoint Name (APN).

An APN is used in 3GPP data access networks (e.g., General Packet RadioService (CPRS) or Evolved Packet Core (EPC) networks) to identify an IPPDN with which a mobile device communicates, and to define a type ofservice provided by the PDN. For example, an APN may identify aconnection to an IP Multimedia Subsystem (IMS), a messaging servicecenter (e.g., a Multimedia Messaging Service Center (MMSC)), a wirelessapplication protocol (WAP) server, the Internet, an application server,or another device, node, and/or service.

In a PDN, an operator's packet domain network is responsible forproviding data connectivity to the mobile user. The user accesses one ormore PDNs, provided by the operator or an external network provided byanother operator. Exemplary PDNs include, but are not limited to,networks providing IMS services, MMS services, WAP services, Internetservices, and visual voicemail (VVM) services. A Gateway GPRS SupportNode (GGSN) provides connectivity between one or more PDNs and theoperator's packet domain network. In general, a user accesses a PDN viaa GGSN, which may be located in a visited operator's network, or may belocated in the user's home operator's network. In some circumstances,inter-operator networks provide IP connectivity between operators'packet domain networks.

An APN is used to identify the PDN from which to provide the user's IPaddress. It is also used to select a GGSN from which the PDN isaccessible. APN resolution is the process of DNS look-up to determinethe IP address of the GGSN that provides connectivity to the PDNidentified by the APN. When a GPRS mobile device activates a PDPcontext, the mobile device provides the APN to which the mobile devicewants to connect. The APN is resolved to identify and to select theappropriate GGSN, and to provide an IP address to the mobile device.When a mobile device sets up a PDP context, the access point is selectedand an APN is determined. This access point is then used in a DNS queryto a private DNS network. This process gives the IP address of the GGSNwhich should serve the access point. At this point a PDP context can beactivated.

SUMMARY

The innovative systems and methods described herein are for managingpacket data protocol (PDP) contexts in a wireless data communicationsnetwork. A plurality of real-time applications are prioritized within asingle, shared PDP context, or allocated a second PDP context based uponpriority levels logically assigned to the plurality of applications,such that high priority applications are delivered before lower priorityapplications. Lower priority applications are suspended and interruptedby higher priority applications and are set to resume after the higherpriority applications are completed. Priority levels are established bya priority management engine (PME) that may reside in one or morenetwork elements, such as a General Packet Radio Service (GPRS) SupportNode (e.g., a GGSN or SGSN) or a network probe system. The prioritymanagement engine establishes the priority levels based upon one or morefactors including, for example, PDP utilization characteristics at agiven time and/or given network location, and/or user preferences.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates a communications network in which someembodiments of the present disclosure may be implemented.

FIG. 2 schematically illustrates an exemplary mobile communicationsdevice and components thereof, according to some embodiments of thepresent disclosure.

FIG. 3 schematically illustrates an exemplary message flow forprioritizing applications within a single shared PDP context, accordingto some embodiments of the present disclosure.

DETAILED DESCRIPTION

As required, detailed embodiments of the present disclosure aredisclosed herein. It must be understood that the disclosed embodimentsare merely exemplary examples of the disclosure that may be embodied invarious and alternative forms, and combinations thereof. As used herein,the word “exemplary” is used expansively to refer to embodiments thatserve as an illustration, specimen, model or pattern. The figures arenot necessarily to scale and some features may be exaggerated orminimized to show details of particular components. In other instances,well-known components, systems, materials or methods have not beendescribed in detail in order to avoid obscuring the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a basis for theclaims and as a representative basis for teaching one skilled in the artto variously employ the present disclosure.

The systems and methods of the present disclosure may be implemented inwireless networks that use exemplary telecommunications standards, suchas Global System for Mobile communications (GSM) and a Universal MobileTelecommunications System (UMTS). It should be understood, however, thatthe systems and methods may be implemented in wireless networks that useany existing or yet to be developed telecommunications technology. Someexamples of other suitable telecommunications technologies include, butare not limited to, networks utilizing Time Division Multiple Access(TDMA), Frequency Division Multiple Access (FDMA), Wideband CodeDivision Multiple Access (WCDMA), Orthogonal Frequency DivisionMultiplexing (OFDM), Long Term Evolution (LTE), and various other 2G,2.5G, 3G, 4G, and greater generation technologies. Examples of suitabledata bearers include, but are not limited to, General Packet RadioService (GPRS), Enhanced Data rates for Global Evolution (EDGE), theHigh-Speed Packet Access (HSPA) protocol family, such as, High-SpeedDownlink Packet Access (HSDPA), Enhanced Uplink (EUL) or otherwisetermed High-Speed Uplink Packet Access (HSDPA), Evolved HSPA (HSPA+),and various other current and future data bearers.

While the processes or methods described herein may, at times, bedescribed in a general context of computer-executable instructions, themethods, procedures, and processes of the present disclosure can also beimplemented in combination with other program modules and/or as acombination of hardware and software. The term application, or variantsthereof, is used expansively herein to include routines, programmodules, programs, components, data structures, algorithms, and thelike. Applications can be implemented on various system configurations,including servers, network systems, single-processor or multiprocessorsystems, minicomputers, mainframe computers, personal computers,hand-held computing devices, mobile devices, microprocessor-basedconsumer electronics, programmable electronics, network elements,gateways, network functions, devices, combinations thereof, and thelike.

Referring now to the drawings in which like numerals represent likeelements throughout the several views, FIG. 1 schematically illustratesan exemplary communications network 100. The communications network 100includes two radio access networks (RANs). A first RAN, illustrated inthe upper left hand portion of FIG. 1, is dedicated to GSM-based networkaccess. A second RAN, illustrated in the lower left hand portion of FIG.1, is dedicated to UMTS-based network access. The innovative aspects ofthe present disclosure may be implemented in alternative networks thatuse other access technologies, as described above. The first RAN is nowdescribed.

The illustrated communications network 100 includes a first MobileStation (MS) 102 and a second MS 104 that are each in communication witha Base Transceiver Station (BTS) 106 via the Um radio (air) interface.The BTSs 106 are terminating nodes for the radio interface in theillustrated first RAN. Each BTS 106 includes one or more transceiversand is responsible for ciphering of the radio interface.

In the illustrated embodiment, the first MS 102 is a mobile device andthe second MS 104 is a computer, such as a laptop with an integrated orexternal, removable GSM access card. Each MS 102, 104 includes mobileequipment, such as, but not limited to, one or more of keyboards,screens, touch screens, multi-touch screens, radio transceivers, circuitboards, processors, memory, Subscriber Identity Modules (SIM), UniversalSIMs (USIM), or Universal Integrated Circuit Card (UICC) that containssubscriber information to enable network access to the wirelesstelecommunications network 100, and the like.

Each BTS 106 is in communication with a Base Station Controller (BSC)108 via the Abis interface. Typically, a BSC has tens or even hundredsof BTSs under its control. The BSC 108 is configured to allocate radioresources to the MSs 102, 104, administer frequencies, and controlhandovers between BTSs 106 (except in the case of an inter-MobileSwitching Center (MSC) handover in which case control is in part theresponsibility of the MSC). One function of the BSC 108 is to act as aconcentrator, so that many different low capacity connections to the BTS106 become reduced to a smaller number of connections towards the MSC.Generally, this means that networks are often structured to have manyBSCs 108 distributed into regions near the BTSs 106, which are in turnconnected to large centralized MSC sites. Although illustrated as adistinct element, the functions provided by the BSC 108 mayalternatively be incorporated in the BTS 106. The Abis interface iseliminated in such a configuration.

The BSC 108 is logically associated with a Packet Control Unit (PCU) 110when GPRS capabilities are employed. The PCU 110 is configured tosupport radio related aspects of GPRS when connected to a GSM network.The PCU 110 is in communication with a Serving GPRS Support Node (SGSN)112 via the Gb interface. The SGSN 112 records and tracks the locationof each mobile device (e.g., MSs 102, 104) in the wirelesstelecommunications network 100. The SGSN 112 also provides securityfunctions and access control functions.

The BSC 108 is also in communication with an MSC 114 via an A interface.The MSC 114 is configured to function as a telecommunications switch.The MSC 114 is in communication with location databases, such as aVisiting Location Register (VLR) 116 and a Home Location Register (HLR)117. The VLR 116 may be logically associated with the MSC 114 asillustrated or may be provided as a separate network element incommunication with the MSC 114. The VLR 116 is a database configured tostore all subscriber data that is required for call processing andmobility management for mobile subscribers that are currently located inan area controlled by the VLR 116.

The HLR 117 is in communication with the MSC 114 and VLR 116 via the Dinterface. The HLR 117 is a database configured to provide routinginformation for mobile terminated calls and various messagingcommunications. The HLR 117 is also configured to maintain subscriberdata that is distributed to the relevant VLR (e.g., the VLR 116) or theSGSN 112 through an attach process and to provide mobility managementprocedures, such as location area and routing area updates. The HLR 117may be logically associated with an Authentication Center (AuC) asillustrated or may be provided as a separate network element incommunication with the HLR 117.

The AuC is configured to authenticate each UICC/SIM/USIM that attemptsto connect to the wireless telecommunications network 100, for example,when a mobile device is powered on. Once authenticated, the HLR 117 isallowed to manage the UICC/SIM/USIM and services provided to the MS 102,104. The AuC also is capable of generating an encryption key that isused to encrypt all wireless communications between the MS 102, 104 andthe communications network 100.

The MSC 114 is also in communication with a Gateway MSC (GMSC) 118 viathe B interface. The GMSC 118 is configured to provide an edge functionwithin a Public Land Mobile Network (PLMN). The GMSC 118 terminatessignaling and traffic from a Public Switched Telephone Network (PSTN)122 and an Integrated Service Digital Network (ISDN) 124, and convertsthe signaling and traffic to protocols employed by the mobile network.The GMSC 118 is in communication with the HLR/AuC 117 via the Cinterface to obtain routing information for mobile terminated callsoriginating from fixed network devices such as, for example, landlinetelephones that are in communication with the mobile network via thePSTN 122.

The MSC 114 is also in communication with an EIR (Equipment IdentityRegister) 128 via an F interface. The EIR 128 is a database that can beconfigured to identify subscriber devices that are permitted to accessthe wireless telecommunications network 100. An IMEI (InternationalMobile Equipment Identity) is a unique identifier that is allocated toeach mobile device and is used to identify subscriber devices in the EIR128. The IMEI includes a type approval code, a final assembly code, aserial number, and a spare digit. An IMEI is typically placed in the EIR128 once its operation has been certified for the infrastructure of thenetwork 100 in a laboratory or validation facility.

The SGSN 112 and the MSC 114 are also in communication with a gatewaymobile location center (GMLC) 129 via an Lg interface. The GMLC 129 cancommunicate with the HLR/AUc 117 via an Lh interface to acquire routinginformation.

The EIR 128 and the HLR/AuC 117 are each in communication with the SGSN112 via the Gf interface and the Gr interface, respectively. The SGSN112, in turn, is in communication with a GGSN (Gateway GPRS SupportNode) 130 via the Gn interface. The GGSN 130 is configured to provide anedge routing function within a GPRS network to external PDNs (PacketData Networks) 132, such as the Internet and one or more intranets, forexample. The GGSN 130 is in communication with the PDN 132 via the Giinterface. The GGSN 130 includes firewall and filtering functionality.The HLR/AuC 117 is in communication with the GGSN 130 via the Gcinterface.

The SGSN 112 is also in communication with other PLMNs 134 via anexternal GGSN (not shown). The external GGSN provides access to theother PLMNs 134. The other PLMNs 134 may be, for example, a foreignnetwork, such as, a wireless telecommunications network operated byanother service provider or the same service provider.

The second RAN, illustrated in the lower left hand portion of FIG. 1, isdedicated to UMTS-based network access and is now described. Theillustrated wireless telecommunications network 100 also includes afirst UE (User Equipment) 136 and a second UE 138 that are each incommunication with a Node B 140 via the Uu radio (air) interface. TheNode B 140 is the terminating node for the radio interface in the secondRAN. Each Node B 140 includes one or more transceivers for transmissionand reception of data across the Uu radio interface. Each Node B 140 isconfigured to apply the codes to describe channels in a CDMA-based UMTSnetwork. Generally, the Node B 140 performs similar functions for theUMTS network that the BTS 106 performs for the GSM network.

In the illustrated embodiment, the first UE 136 is a mobile phone (e.g.,the mobile device 102, 800) and the second UE 138 is a computer, such asa laptop with an integrated or external, removable UMTS card. Each UE136, 138 includes mobile equipment, such as one or more of keyboards,screens, touch screens, multi-touch screens, radio transceivers, circuitboards, processors, memory, SIMs, USIMs, or UICCs that containssubscriber information to enable network access to the wirelesstelecommunications network 100, and the like. Generally, the UE's 136,138 perform similar functions in the UMTS network that the MS's 102, 104perform in the GSM network.

Each Node B 140 is in communication with a Radio Network Controller(RNC) 142 via the lub interface. The RNC 142 is configured to allocateradio resources to the UE's 136, 138, administer frequencies, andcontrol handovers between Node Bs 140 (and others not shown). Althoughillustrated as a distinct element, the RNC 142 functions mayalternatively be located within the Node Bs 140. In this configurationthe lub interface is eliminated. Generally, the RNC 142 performs similarfunctions for the UMTS network that the BSC 108 performs for the GSMnetwork.

The RNC 142 is in communication with the MSC 114 via an lu-CS interface.The RNC 142 is also in communication with the SGSN 112 via an lu-PSinterface. The other network elements perform the same functions for theUMTS network as described above for the GSM network.

The communications network 100 also includes an IP Multimedia Subsystem(IMS) network 144. The IMS network 144 includes Call State ControlFunctions (CSCFs), such as, a Proxy-CSCF (P-CSCF), an Interrogating-CSCF(I-CSCF), and a Serving-CSCF (S-CSCF). A P-CSCF is the first contactpoint in the IMS network 144 for a UE and routes incoming communicationsto the I-CSCF. The I-CSCF determines which S-CSCF is serving thecommunication and routes the communication to that S-CSCF, whichperforms registration, session control, and application interfacefunctions. The P-CSCF and the I-CSCF are illustrated as a combinedI/P-CSCF 146 and the S-CSCF 148 is illustrated as a stand-alone element.Other CSCF configurations are contemplated.

The IMS network 144 also includes a Home Subscriber Server (HSS) 150,which is a master user database that supports the IMS network 144 corenetwork elements. The HSS 150 stores subscription-related information,such as subscriber account details and subscriber profiles, performsauthentication and authorization of the user, and provides informationabout a subscriber's location and IP address. It is similar to the GSMHLR and AuC, described above as the combination HLR/AuC 117.

The IMS network 144 also includes a Media Gateway Control Function(MGCF) 152, which provides call control protocol conversions between theISUP (ISDN User Part) protocol used by the PSTN 122 and the SIP (SessionInitiation Protocol) used by the IMS network 144.

Referring back to the SGSN 112, it is shown that the SGSN 112 is incommunication with a charging system 154 via a CAP interface. The GGSN130 is also in communication with the charging system 154, via an Rointerface. The charging system 154, in turn, is in communication with abilling system 156.

Briefly, the charging system 154 is responsible for offline and onlinecharging of subscriber accounts. The charging system 154 may be deployedto provide charging rule functions for prepaid and/or postpaid networkplatforms. The single charging system 154 is illustrated for simplicity,however separate charging systems are contemplated and may be utilizedif desired by the operating service provider.

The billing system 156 is responsible for billing postpaid customers andhandling payments received for service provisioned for both postpaid andprepaid accounts in the network 100. Like the charging system 154, thebilling system 156 may alternatively be designed as two separateentities for postpaid and prepaid applications.

The SGSN 112 is also in communication with a Domain Name System (DNS)server 158 via an exemplary X₁ interface. The SGSN 112, the DNS server158 and the GGSN 130 communicate with one another during a PDP contextactivation sequence.

An exemplary PDP context activation sequence begins when a requestingmobile device (e.g., one of devices 102, 104, 136, 138) initiates thePDP context activation sequence to obtain the IP address for the device.The APN is specified by the APN is passed as a parameter in an activatePDP context message. A service identification (service ID) is alsoincluded in the activate PDP context message. The service ID identifiesthe service the requesting mobile device is attempting to access. Uponreceipt of the activate PDP context message, the SGSN 112 initiates aDNS query to the DNS server 158 to resolve an IP address for the GGSN(e.g., the GGSN 130) corresponding to the APN. The DNS server 158provides the GGSN IP address to the SGSN 112, which uses the IP addressto initiate a create PDP context request to the GGSN 130 correspondingto the APN.

The GGSN 130 is also in communication with an authentication server 160via an exemplary X₂ interface, a Dynamic Host Configuration Protocol(DHCP) server 162 via an exemplary X₃ interface, and a prioritymanagement engine (PME) 164 via an exemplary X₄ interface. The GGSN 130authenticates GPRS subscription information with the authenticationserver 160. The authentication server 160 operates using the RADIUSprotocol or the DIAMETER protocol to authenticate subscriptioninformation prior to allowing a requesting mobile device to activate aPDP context. The authentication server 160 then notifies the GGSN 130 ofthe success/failure of the subscription authentication. Upon receivingnotification of a successful authentication, the GGSN 130 communicateswith the DHCP server 162 to retrieve a dynamic IP address for use in thePDP context. The GGSN 130 then requests a priority level for the serviceidentified in the service 1D from the PME 164.

The PME 164 is configured to store priority levels for services offeredby the service provider including, but not limited to, visual voicemail(VVM) service, Internet access, audio streaming, video streaming, onlinegaming, Internet television, and other applications that require a dataconnection. While priorities may be established for any application thatutilizes a data connection, priorities established for applications thatare time-sensitive, delay-sensitive, location-specific, network resourceintensive, or some combination thereof may experience greater benefitfrom the discloses systems and methods.

A user may assign priority levels to data applications operating ontheir device. The device may upload the priority levels to the PME 164for consideration during a PDP context activation sequence, as describedin greater detail below with reference to FIG. 3.

Alternatively, a service provider may assign priority levels for dataapplications based upon various factors including, for example, networkload information retrieved from network analysis equipment (e.g.,network probes, BTSs, MSCs, hardware/software components used in cellsite planning and/or maintenance, and the like), geographical factors,and subscriber feedback regarding slow, poor, or no connection. Inaddition, service providers may seek to optimize subscriber experiencesfor certain applications. For example, a service provider may assign atop priority level to WM service such that a WM application resident ona subscriber's device is given priority over other services that mayotherwise interfere with the WM application obtaining new voicemailsfrom a voicemail server.

Upon request from the GGSN 130, the PME 164 may return the assignedpriority level for a service. The GGSN 130 may store the priority levelfor the requested service to use in comparisons with priority levels forservices in subsequent service requests. For example, if a firstrequested service is web browsing followed by a WM application, the webbrowsing service would temporarily be suspended to allow the VVMapplication to retrieve a new voicemail. At a time thereafter, the webbrowsing service is reactivated. The functionality of the PME 164 isdescribed in greater detail below with reference to FIG. 3.

Referring now to FIG. 2, a schematic block diagram of an exemplarymobile device 200 is illustrated. Although connections are not shownbetween the components illustrated in FIG. 2, the components caninteract with each other to carry out device functions. In someembodiments, for example, the components are arranged so as tocommunicate via one or more busses (not shown). It should be understoodthat FIG. 2 and the following description are intended to provide ageneral understanding of a suitable environment in which the variousaspects of some embodiments of the present disclosure can beimplemented.

In some embodiments, the mobile devices 102, 104, 136, 138 illustratedin FIG. 1 are configured like the mobile device 200, now described indetail. In some embodiments, the mobile device 200 is a multimodeheadset and has a variety of computer-readable media, including, forexample, volatile media, non-volatile media, removable media, andnon-removable media. The term computer-readable media and variantsthereof, as used in the specification and claims, refer to storage mediaand communication media. In some embodiments, storage media includesvolatile and/or non-volatile, removable, and/or non-removable media. Forexample, storage media includes random access memory (RAM), read-onlymemory (ROM), electrically erasable programmable read-only memory(EEPROM), solid state memory or other memory technology, CD ROM, DVD, orother optical disk storage, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other tangible medium that can beused to store the desired information and that can be accessed by themobile device 200.

As illustrated in FIG. 2, the mobile device 200 includes a display 202for displaying multimedia such as, for example, voicemail notificationmessages, application graphical user interfaces (GUIs), text, images,video, telephony functions, such as Caller ID data, setup functions,menus, voicemail message waiting identifiers (MWIs), music, metadata,messages, wallpaper, graphics, Internet content, device status,preferences settings, map and location data, profile (e.g., vibrate,silent, loud) selection, and the like. The display 202 may displayvisual voicemail data in visual voicemail headers, such as the date,time, message length, message status (i.e., new-unread, read, saved, ordeleted), and calling line identity (CLI) information. The illustratedmobile device 200 also includes a processor 204 for processing dataand/or executing computer-executable instructions of one or moreapplications 208, and a memory 206 for storing data and/or one or moreof the applications.

In some embodiments, the application(s) 208 include a user interface(UI) application 210. The UI application 210 interfaces with a client212 (e.g., an operating system (OS)) to facilitate user interaction withdevice functionality and data. In some embodiments, the client 212 isone of Symbian OS, Microsoft® Windows® Mobile OS (available fromMicrosoft Corporation of Redmond, Wash.), Palm® webOS™ (available fromPalm Corporation of Sunnyvale, Calif.), Palm® OS (available from PalmCorporation), RIM® BlackBerry® OS (available from Research In MotionLimited of Waterloo, Ontario, Canada), Apple® iPhone® OS (available fromApple Corporation of Cupertino, Calif.), or Google Android™ OS(available from Google Inc. of Mountain View, Calif.). These operatingsystems are merely exemplary of the operating systems that may be usedin accordance with the embodiments disclosed herein.

The UI application 210 aids a user in entering message content, viewingreceived messages (e.g., multimedia messages, SMS messages, visualvoicemail messages), managing voicemails in a visual voicemailapplication, answering/initiating calls, entering/deleting data,entering and setting user IDs and passwords for device access,configuring settings, manipulating address book content and/or settings,multimode interaction, interacting with other applications 214, and thelike. In some embodiments, the other applications 214 include, forexample, visual voicemail applications, messaging applications (e.g.,SMS, EMS, MMS applications), presence applications, text-to-speechapplications, speech-to-text applications, add-ons, plug-ins, emailapplications, music applications, video applications, cameraapplications, location service applications (LSAs), power conservationapplications, game applications, productivity applications,entertainment applications, enterprise applications, combinationsthereof, and the like. The applications 208 are stored in the memory 206and/or in a firmware 216, and are executed by the processor 204. Thefirmware 216 may also store code for execution during device power up,for example.

The mobile device 200 also includes a device-based priority managementengine (PME) 215. In some embodiments, the device PME 215 is configuredto determine a priority for a requested application and request thedetermined priority when establishing a PDP context or using an existingPDP context. By way of example, the device PME 215 may determine apriority for a requested application based upon various factorsincluding, but not limited to, a current time, a current devicelocation, a serving network location, associated network load at theserving network location (e.g., SGSN, GGSN, RNC, BSC, MSC BTS, node-Bloads), requested application type (e.g., real-time or delay-sensitiveapplication vs. non-real-time or non-delay-sensitive application), userpreferences (e.g., user-defined priorities for applications).

In some embodiments, the device PME 215 is configured to append apriority level to an Activate PDP Context request for a requestedapplication sent from the mobile device 200 to the SGSN 112. The SGSN112 may forward the priority level to the network PME 164 or the GGSN130, whereat it is determined whether access to the requestedapplication can be provided at the requested priority level.Alternatively, the SGSN 112 makes this determination.

In the case that at least one other application is running on the mobiledevice 200 when the mobile device 200 requests access to the requestedapplication, the PME 164, GGSN 130, or SGSN 112, as appropriate, willdetermine whether network resources and other factors, such as thosedescribed above but from the network's perspective, permit a new PDPcontext to be established for the requested application. Alternatively,an application utilizing an existing PDP context may be suspended if itis assigned a lower priority than the priority level of the requestedapplication. The suspended application may be allowed to resume use of aPDP context after the requested application is terminated. This isparticularly useful for applications that use the same APN.

For applications that use different APNs, a new PDP context may need tobe established. Alternatively, in some embodiments, applications aredynamically routed to APNs to further conserve network resources. Forexample, a WM application may be routed to use an Internet APN if a PDPcontext has already been established for an Internet application, suchas video streaming, audio streaming, Internet browsing, and the like. Inthis example, routing functions are appropriately deployed with thenetwork to facilitate such a feature.

In some embodiments, a priority level is established by the device PME215 and is the only priority level established for a given application.In other embodiments, the device PME 215 suggests a priority level thatmay be accepted or rejected by the network PME 164, the GGSN 130, theSGSN 112 or other serving node. In still other embodiments, describedbelow with reference to FIG. 3, priority levels are managed in thenetwork at the PME 164 and PDP contexts are selectively suspended,activated, or deactivated based upon the priority levels established bythe PME 164 based upon user preferences, location, service providerpreferences, network load preferences, and other criteria describedabove.

The illustrated mobile device 200 also includes an input/output (I/O)interface 218 for input/output of data, such as, for example, voicemailaccount information requests, visual voicemail management, locationinformation, presence status information, user IDs, passwords, andapplication initiation (start-up) requests. In some embodiments, the I/Ointerface 218 is a hardwire connection, such as, for example, a USB,mini-USB, audio jack, PS2, IEEE 1394, serial, parallel, Ethernet (RJ48)port, RJ11 port, or the like. In some embodiments, the I/O interface 218accepts other I/O devices such as, for example, keyboards, keypads,mice, interface tethers, stylus pens, printers, thumb drives, touchscreens, multi-touch screens, touch pads, trackballs, joysticks,microphones, remote control devices, monitors, displays, liquid crystaldisplays (LCDs), combinations thereof, and the like. It should beappreciated that the I/O interface 218 may be used for communicationsbetween the mobile device 200 and a network or local device, instead of,or in addition to, a communications component 220.

The communications component 220 interfaces with the processor 204 tofacilitate wired/wireless communications with external systems. Exampleexternal systems include, but are not limited to, intranets, networkdatabases, network storage systems, cellular networks, location servers,presence servers, Voice over Internet Protocol (VoIP) networks, localarea networks (LANs), wide area networks (WANs), metropolitan areanetworks (MANs), personal area networks (PANs), and other networks. Insome embodiments, the external systems are implemented using WIFI,WIMAX, combinations and/or improvements thereof, and the like. In someembodiments, the communications component 220 includes a multimodecommunications subsystem for providing cellular communications viadifferent cellular technologies. In some embodiments, for example, afirst cellular transceiver 222 operates in one mode, such as, GSM, andan Nth cellular transceiver 224 operates in a different mode, such asUMTS. While only two cellular transceivers 222, 224 are illustrated, itshould be appreciated that a plurality of transceivers can be included.

The illustrated communications component 220 also includes analternative communications transceiver 226 for use by othercommunications technologies such as, for example, WIFI, WIMAX,BLUETOOTH, infrared, infrared data association (IRDA), near fieldcommunications (NFC), RF, and the like. In some embodiments, thecommunications component 220 also facilitates reception from terrestrialradio networks, digital satellite radio networks, Internet-based radioservices networks, combinations thereof, and the like.

The communications component 220 processes data from a network such as,for example, the Internet, an intranet (e.g., business intranet), a homebroadband network, a WIFI hotspot, and the like, via an ISP, DSLprovider, or broadband provider. In some embodiments, the communicationscomponent 220 facilitates the transmission of authentication informationfrom the mobile device 200 to a network for processing in accordancewith the methods described herein.

Audio capabilities for the mobile device 200 can be provided by an audioI/O component 228 that includes a speaker for the output of audiosignals and a microphone to collect audio signals.

The illustrated mobile device 200 also includes a slot interface 230 foraccommodating a subscriber identity system 232 such as, for example, asubscriber identity module (SIM) card, universal SIM (USIM) card, oruniversal integrated circuit card (UICC) including one or more SIMapplications (e.g., ISIM, SIM, USIM, CSIM). Alternatively, thesubscriber identity system 232 may be manufactured into the mobiledevice 200, thereby obviating the need for a slot interface 230. In someembodiments, the subscriber identity system 232 is programmed by amanufacturer, a retailer, a user, a computer, a network operator, or thelike. The subscriber identity system 232 may be configured to storevoicemail account information, contact information for the user and/oraddress book contacts, and/or other information.

The illustrated mobile device 200 also includes an image capture andprocessing system 234 (image system). Photos may be obtained via anassociated image capture subsystem of the image system 234, for example,a camera. The illustrated mobile device 200 also includes a video system236 for capturing, processing, recording, modifying, and/or transmittingvideo content. Photos and videos obtained using the image system 234 andthe video system 236, respectively, may be added as message content toan MMS message and sent to another mobile device.

The illustrated mobile device 200 also includes a location component 238for sending and/or receiving signals such as, for example, GPS data,assisted GPS (A-GPS) data, WIFI/WIMAX and/or cellular networktriangulation data, combinations thereof, and the like, for determininga location of the mobile device 200. In some embodiments, the locationcomponent 238 interfaces with cellular network nodes, telephone lines,satellites, location transmitters and/or beacons, wireless networktransmitters and receivers, for example, WIFI hotspots, radiotransmitters, combinations thereof, and the like. Using the locationcomponent 238, the mobile device 200 obtains, generates, and/or receivesdata to identify its location, or transmits data used by other devicesto determine the location of the mobile device 200.

The illustrated mobile device 200 also includes a power source 240, suchas batteries and/or other power subsystem (AC or DC). The power source240 can interface with an external power system or charging equipmentvia a power I/O component 242.

Referring now to FIG. 3, an exemplary message flow diagram forprioritizing applications within a single shared PDP context isschematically illustrated. The message flow begins, at step 300, when aservice (application) request is received at the mobile device 200. Asillustrated, a service request for service 1 is requested. This promptsthe mobile device 200 to request a PDP context to be activated to accessservice 1 through APN 1. APN 1 is appended to the request. The requestis formatted as an Activate PDP Context request as is typical for a PDPcontext activation sequence.

At step 302, the Activate PDP Context request is sent to the SGSN 112.At step 304, the SGSN 112 initiates a DNS query to the DNS server 158 tofind the GGSN (e.g., the GGSN 130) corresponding to the APN specified bythe mobile device 200 in the Activate PDP Context request. At step 306,the DNS server 158 provides the IP address for the serving GGSN(illustrated as the GGSN 130) to the SGSN 112. At step 308, the SGSN 112sends a Create PDP Context request to the GGSN 130 corresponding to theAPN. At step 310, the GGSN 130 sends an authentication request to theauthentication server 160 to authenticate the data service (e.g., GPRS)account of the subscriber associated with the mobile device 200. Theauthentication server 160 authenticates the GPRS subscription andreplies back to the GGSN 130, at step 312. At step 314, the GGSN 130requests a dynamic IP address from the DHCP server 162. At step 316, theDHCP server 162 returns an IP address to the GGSN 130.

At step 318, the GGSN 130 requests a priority level from the PME 164 ina Priority Req (Service_(—)1) message. At step 320, the PME 164 returnsthe assigned priority level for service 1 to the GGSN 130. The GGSN 130may store the priority level for service 1 to use in comparisons withpriority levels for services in subsequent service requests. At step322, the GGSN 130 responds to the SGSN 112 with the IP address. At step324, the SGSN 112 replies back to the mobile device 200 to signalcompletion of the PDP context activation sequence.

At this point, a PDP context has been established between the mobiledevice 200 and APN 1 to facilitate access to service 1. This PDP contextis illustrated as PDP context A with service 1 active via APN 1 (326).At step 328, the mobile device 200 receives a second service request forservice 2 also on APN 1. Upon receipt of the second service request, atstep 330, the mobile device 200 sends an Activate PDP Context requestfor service 2 to the SGSN 112. At step 332, upon receipt of the ActivatePDP Context request and based upon the known established PDP context A,the SGSN 112 sends a Get_Priority_Lvls message to the GGSN 130 torequest the priority level for the requested application (service 2) andthe presently served application (service 1).

At step 334, the PME 164 sends a Priority Req message to the PME 164. Ifthe GGSN 130 has not stored the priority level for service 1, at step336, the PME 164 sends both priority levels in a Priority Resp messageto the GGSN 130. Alternatively, at step 336, if the GGSN 130 has storedthe priority level for service 1, the PME 164 returns only the prioritylevel for service 2. In general, the GGSN 130 is configured to comparethe priority levels for both (or any number of) services and instructthe SGSN 112 to respond to the Activate PDP Context requestappropriately depending upon whether service 2 is assigned a higherpriority level than service 1.

Alternatively, at step 334, the GGSN 130 sends a Priority Cmp message tothe PME 164, instructing the PME 164 to compare the priority level forany existing service (e.g., service 1 in the illustrated embodiment) tothe priority level for the requested service which, in this case, isservice 2. In the illustrated embodiment, the PME 164 returns service 2as having the highest priority.

At step 338, the GGSN 130 returns the highest priority service to theSGSN 112. At step 340, the SGSN 112 responds to the mobile device'sActivate PDP Context request with at PDP Accept message for service 2.This response causes the mobile device 200 to suspend PDP context A forservice 1 and PDP context A is used for service 2. After service 2 is nolonger needed, the mobile device 200 reverts back to service 1 using PDPcontext A without needing to reestablish a PDP context or utilize anadditional PDP context.

The illustrated embodiments allow the mobile device 200 to performnormally in requesting PDP contexts and do not necessarily need to haveknowledge of a particular service's priority level. As such, the firstActivate PDP context request is typical, as is the second Activate PDPcontext request. The SGSN 112, the GGSN 130, and the PME 164 communicateto determine the priority for a requested service and return a PDPcontext accept message to the mobile device 200, instructing the mobiledevice 200 to access the higher priority service using the establishedPDP context A. The illustrated embodiment is not limited to twoapplications and is equally applicable to three or more applications.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely exemplaryillustrations of implementations set forth for a clear understanding ofthe principles of the disclosure. Variations, modifications, andcombinations may be made to the above-described embodiments withoutdeparting from the scope of the claims. All such variations,modifications, and combinations are included herein by the scope of thisdisclosure and the following claims.

1. A method for managing packet data protocol contexts in a wirelessdata communications network, the method comprising: receiving, at agateway support node, a create packet data protocol context request froma serving gateway support node to create a packet data protocol context,the create packet data protocol context request comprising a firstservice identifier associated with a first requested service and anaccess point name, and the create packet data protocol context requestbeing received at the gateway support node from the serving gatewaysupport node in response to the serving gateway support node receiving afirst activate packet data protocol context message from a mobile devicerequesting the first requested service; the gateway support nodegenerating a first priority request for the first requested service, thefirst priority request comprising the first service identifier; thegateway support node sending the first priority request to a prioritymanagement engine, which determines a first priority level associatedwith the first requested service; the gateway support node receivingfrom the priority management engine in response to the first priorityrequest, the first priority level associated with the first requestedservice; the gateway support node generating a create packet dataprotocol context response and sending the create packet data protocolcontext response to the serving gateway support node, which creates thefirst packet data protocol context for the first service via the accesspoint name so that the mobile device can access the first service andnotifies the mobile device of the creation of the first packet dataprotocol context with a first packet data protocol context acceptmessage in response to the first activate packet data protocol contextmessage; the gateway support node receiving a get priority message fromthe serving support node, the get priority message comprising a requestfor the first priority level of the first requested service and a secondpriority level for a second service requested in a second activatepacket data protocol context message received at the serving supportnode from the mobile device; the gateway support node generating, inresponse to the get priority message, a second priority request for thesecond requested service, the second priority request comprising asecond service identifier associated with the second requested service;the gateway support node sending the second priority request to thepriority management engine, which determines a second priority levelassociated with the second requested service; the gateway support nodereceiving from the priority management engine, in response to the secondpriority request, the second priority level associated with the secondrequested service; the gateway support node comparing the first prioritylevel to the second priority level to determine which of the first andsecond requested services is a highest priority service; the gatewaysupport node generating a priority response comprising an indication ofthe highest priority service; and the gateway support node sending thepriority response to the serving gateway support node.
 2. The method ofclaim 1, wherein the gateway support node sends the first priorityrequest and the second priority request to the priority managementengine, which determines the first priority level associated with thefirst requested service and the second priority level associated withthe second requested service, the first priority level being determinedby the priority management engine for the first requested service basedupon a priority factor established for the first requested service andthe second priority level being determined by the priority managementengine for the second requested service based upon a priority factorestablished for the second requested service, wherein the priorityfactors are selected from a group consisting of a network load factor, ageographical factor, a user preference factor, a subscriber feedbackfactor, a user specified factor, a service provider specified factor, anservice-specific factor, a time-sensitive factor, a delay-sensitivefactor, a location-specific factor, and a network resource factor. 3.The method of claim 1, wherein the gateway support node comparing thefirst priority level to the second priority level to determine which ofthe first and second requested services is the highest priority servicecomprises the gateway support node comparing the first priority level,stored at the gateway support node after receiving the first prioritylevel from the priority management engine in response to the firstpriority request, to the second priority level received from thepriority management engine in response to the second priority request.4. The method of claim 1, wherein the second packet data protocolcontext accept message, with which the serving gateway support noderesponds to the second activate packet data protocol context messagefrom the mobile device, comprises the indication of the highest priorityservice and instructions to: suspend the first requested service if thefirst priority level is lower than the second priority level; or allowthe first requested service to conclude prior to the second requestedservice being activated if the second priority level is lower than thefirst priority level.
 5. The method of claim 1, wherein: the gatewaysupport node sending the second priority request to the prioritymanagement engine comprises the gateway support node requesting thefirst priority level and the second priority level from the prioritymanagement engine; and the gateway support node comparing the firstpriority level to the second priority level to determine which of thefirst and second requested services is the highest priority servicecomprises the gateway support node comparing the first priority levelreceived from the priority management engine in the second priorityrequest and the second priority level received from the prioritymanagement engine in the second priority request.
 6. The method of claim2, wherein the first requested service is a visual voicemail service andthe priority factor for the first priority level indicates that thevisual voicemail service is by default the highest priority service suchthat: the gateway support node comparing the first priority level to thesecond priority level to determine which of the first and secondrequested services is the highest priority service always results in thegateway support node generating the priority response comprising anindication of the visual voicemail service being the highest priorityservice.
 7. The method of claim 1, wherein the first requested serviceand the second requested service are each selected from a group ofservices consisting of: a visual voicemail service, an Internet accessservice, an audio streaming service, a video streaming service, anonline gaming service, an Internet television service, a serviceassociated with a data application stored on the mobile device, aservice associated with a data application accessible by the mobiledevice via an Internet application stored on the mobile device, atime-sensitive service, a delay-sensitive service, a location-specificservice, and a network resource intensive service.
 8. A non-transitorycomputer-readable medium of a gateway support node comprisingcomputer-executable instructions which, when executed, cause a processorof the gateway support node to: receive a create packet data protocolcontext request from a serving gateway support node to create a packetdata protocol context, the create packet data protocol context requestcomprising a first service identifier associated with a first requestedservice and an access point name, and the create packet data protocolcontext request being received from the serving gateway support node inresponse to the serving gateway support node receiving a first activatepacket data protocol context message from a mobile device requesting thefirst requested service; generate a first priority request for the firstrequested service, the first priority request comprising the firstservice identifier; send the first priority request to a prioritymanagement engine, which determines a first priority level associatedwith the first requested service; receive from the priority managementengine, in response to the first priority request, the first prioritylevel associated with the first requested service; generate a createpacket data protocol context response and sending the create prioritymanagement engine context response to the serving gateway support node,which creates the first packet data protocol context for the firstservice via the access point name so that the mobile device can accessthe first service and notifies the mobile device of the creation of thefirst packet data protocol context with a first packet data protocolcontext accept message in response to the first activate packet dataprotocol context message; receive a get priority message from theserving gateway support node, the get priority message comprising arequest for the first priority level of the first requested service anda second priority level for a second service requested in a secondactivate packet data protocol context message received at the servinggateway support node from the mobile device; generate, in response tothe get priority message, a second priority request for the secondrequested service, the second priority request comprising a secondservice identifier associated with the second requested service; sendthe second priority request to the priority management engine, whichdetermines a second priority level associated with the second requestedservice; receive from the priority management engine, in response to thesecond priority request, the second priority level associated with thesecond requested service; compare the first priority level to the secondpriority level to determine which of the first and second requestedservices is a highest priority service; generate a priority responsecomprising an indication of the highest priority service; and send thepriority response to the serving gateway support node.
 9. Thenon-transitory computer-readable medium of claim 8, wherein the prioritymanagement engine determines the first priority level associated withthe first requested service and the second priority level associatedwith the second requested service, the first priority level beingdetermined by the priority management engine for the first requestedservice based upon a priority factor established for the first requestedservice and the second priority level being determined by the prioritymanagement engine for the second requested service based upon a priorityfactor established for the second requested service, the priorityfactors selected from a group consisting of a network load factor, ageographical factor, a user preference factor, a subscriber feedbackfactor, a user specified factor, a service provider specified factor, anservice-specific factor, a time-sensitive factor, a delay-sensitivefactor, a location-specific factor, and a network resource factor. 10.The non-transitory computer-readable medium of claim 8, wherein theinstructions which cause the processor to compare the first prioritylevel to the second priority level to determine which of the first andsecond requested services is the highest priority service furthercomprise instructions which cause the processor to compare the firstpriority level, stored at computer-readable medium after receiving thefirst priority level from the priority management engine in response tothe first priority request, to the second priority level received fromthe priority management engine in response to the second priorityrequest.
 11. The non-transitory computer-readable medium of claim 8,wherein the second packet data protocol context accept message, withwhich the serving gateway support node responds to the second activatepacket data protocol context message from the mobile device, comprisesthe indication of the highest priority service and instructions to:suspend the first requested service if the first priority level is lowerthan the second priority level; or allow the first requested service toconclude prior to the second requested service being activated if thesecond priority level is lower than the first priority level.
 12. Thenon-transitory computer-readable medium of claim 8, wherein: theinstructions which cause the processor to send the second priorityrequest to the priority management engine further comprise instructionswhich cause the processor to request the first priority level and thesecond priority level from the priority management engine; and theinstructions which cause the processor to compare the first prioritylevel to the second priority level to determine which of the first andsecond requested services is the highest priority service furthercomprise instructions which cause the processor to compare the firstpriority level received from the priority management engine in thesecond priority request and the second priority level received from thepriority management engine in the second priority request.
 13. Thenon-transitory computer-readable medium of claim 9, wherein the firstrequested service is a visual voicemail service and the priority factorfor the first priority level indicates that the visual voicemail serviceis by default the highest priority service such that: the instructionswhich cause the processor to compare the first priority level to thesecond priority level to determine which of the first and secondrequested services is the highest priority service always results in thegateway support node generating the priority response comprising anindication of the visual voicemail service being the highest priorityservice.
 14. The non-transitory computer-readable medium of claim 8,wherein the first requested service and the second requested service areeach selected from a group of services consisting of: a visual voicemailservice, an Internet access service, an audio streaming service, a videostreaming service, an online gaming service, an Internet televisionservice, a service associated with a data application stored on themobile device, a service associated with a data application accessibleby the mobile device via an Internet application stored on the mobiledevice, a time-sensitive service, a delay-sensitive service, alocation-specific service, and a network resource intensive service. 15.A gateway support node, comprising: a transceiver configured tofacilitate communication with a serving gateway support node and apriority management engine; a processor; a memory, in communication withthe processor, the memory configured store instructions, which areexecutable by the processor to: receive a create packet data protocolcontext request from the serving gateway support node to create a packetdata protocol context, the create packet data protocol context requestcomprising a first service identifier associated with a first requestedservice and an access point name, and the create packet data protocolcontext request being received from the serving gateway support node inresponse to the serving gateway support node receiving a first activatepacket data protocol context message from a mobile device requesting thefirst requested service; generate a first priority request for the firstrequested service, the first priority request comprising the firstservice identifier; send the first priority request to the prioritymanagement engine, which determines a first priority level associatedwith the first requested service, the first priority level beingdetermined by the priority management engine for the first requestedservice; receive from the priority management engine, in response to thefirst priority request, the first priority level associated with thefirst requested service; generate a create packet data protocol contextresponse and sending the create packet data protocol context response tothe serving gateway support node, which creates the first packet dataprotocol context for the first service via the access point name so thatthe mobile device can access the firs service and notifies the mobiledevice of the creation of the first packet data protocol context with afirst packet data protocol context accept message in response to thefirst activate packet data protocol context message; receive a getpriority message from the serving gateway support node, the get prioritymessage comprising a request for the first priority level of the firstrequested service and a second priority level for a second servicerequested in a second activate packet data protocol context messagereceived at the serving gateway support node from the mobile device;generate, in response to the get priority message, a second priorityrequest for the second requested service, the second priority requestcomprising a second service identifier associated with the secondrequested service; send the second priority request to the prioritymanagement engine, which determines a second priority level associatedwith the second requested service, the second priority level beingdetermined by the priority management engine for the second requestedservice; receive from the priority management engine, in response to thesecond priority request, the second priority level associated with thesecond requested service; compare the first priority level to the secondpriority level to determine which of the first and second requestedservices is a highest priority service; generate a priority responsecomprising an indication of the highest priority service; and send thepriority response to the serving gateway support node.
 16. The gatewaysupport node of claim 15, wherein the instructions are executable by theprocessor to send the first priority request and the second priorityrequest to the priority management engine, which determines the firstpriority level associated with the first requested service and thesecond priority level associated with the second requested service, thefirst priority level being determined by the priority management enginefor the first requested service based upon a priority factor establishedfor the first requested service and the second priority level beingdetermined by the priority management engine for the second requestedservice based upon a priority factor established for the secondrequested service further comprise instructions indicating that thepriority factors are selected from a group consisting of: a network loadfactor, a geographical factor, a user preference factor, a subscriberfeedback factor, a user specified factor, a service provider specifiedfactor, an service-specific factor, a time-sensitive factor, adelay-sensitive factor, a location-specific factor, and a networkresource factor.
 17. The general packet radio service gateway supportnode of claim 15, wherein the instructions, which are executable by theprocessor to compare the first priority level to the second prioritylevel to determine which of the first and second requested services isthe highest priority service further comprise instructions, which areexecutable by the processor to compare the first priority level, storedin the memory after receiving the first priority level from the prioritymanagement engine in response to the first priority request, to thesecond priority level received from the priority management engine inresponse to the second priority request; and wherein the second packetdata protocol context accept message, with which the serving gatewaysupport node responds to the second activate packet data protocolcontext message from the mobile device comprises the indication of thehighest priority service and instructions to: suspend the firstrequested service if the first priority level is lower than the secondpriority level; or allow the first requested service to conclude priorto the second requested service being activated if the second prioritylevel is lower than the first priority level.
 18. The gateway supportnode claim 15, wherein the instructions, which are executable by theprocessor to: send the second priority request to the prioritymanagement engine further comprise instructions, which are executable bythe processor to request the first priority level and the secondpriority level from the priority management engine; and compare thefirst priority level to the second priority level to determine which ofthe first and second requested services is the highest priority servicefurther comprise instructions, which are executable by the processor tocompare the first priority level received from the priority managementengine in the second priority request and the second priority levelreceived from the priority management engine in the second priorityrequest.
 19. The gateway support node of claim 16, wherein the firstrequested service is a visual voicemail service and the priority factorfor the first priority level indicates that the visual voicemail serviceis by default the highest priority service such that: the instructions,which are executable by the processor to compare the first prioritylevel to the second priority level to determine which of the first andsecond requested services is the highest priority service always resultsin the general packet radio service gateway support node generating thepriority response comprising an indication of the visual voicemailservice being the highest priority service.
 20. The gateway support nodeof claim 15, wherein the first requested service and the secondrequested service are each selected from a group of services consistingof: a visual voicemail service, an Internet access service, an audiostreaming service, a video streaming service, an online gaming service,an Internet television service, a service associated with a dataapplication stored on the mobile device, a service associated with adata application accessible by the mobile device via an Internetapplication stored on the mobile device, a time-sensitive service, adelay-sensitive service, a location-specific service, and a networkresource intensive service.